FHIR © HL7.org  |  Server Home  |  FHIR Server FHIR Server 3.7.16  |  FHIR Version n/a  User: [n/a]

Resource Requirements/FHIR Server from package hl7.ehrs.uv.phrsfmr2#current (31 ms)

Package hl7.ehrs.uv.phrsfmr2
Type Requirements
Id Id
FHIR Version R5
Source http://hl7.org/ehrs/uv/phrsfmr2/https://build.fhir.org/ig/HL7/phrsfm-ig/Requirements-PHRSFMR2-S.3.3.2.html
Url http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-S.3.3.2
Version 2.0.1-ballot
Status active
Date 2025-04-03T15:15:30+00:00
Name S_3_3_2_Manage_End_of_Life_Documents_and_Other_Advance_Directives
Title S.3.3.2 Manage End-of-Life Documents and Other Advance Directives (Function)
Experimental False
Authority hl7
Description Manage documents that provide direction for end-of-life care and manage other types of Advance Directives.
Purpose The PHR Account Holder may want to capture and maintain documents that pertain to end-of-life care and to capture and maintain other types of Advance Directives. End-of-life documents include but are not limited to: Advance Directive for Healthcare; Power of Attorney for Healthcare and Physician Order for Life Sustaining Treatment. The system should allow for multiple occurrences of a document and the ability to archive documents. The documents maintained will depend on the jurisdictional law. The documents may or may not reside in the PHR-S. The document may be scanned images, structured documents or simply a notation on the location of the original (hardcopy or original).

Resources that use this resource

No resources found


Resources that this resource uses

No resources found



Narrative

Note: links and images are rebased to the (stated) source

Statement N:

Manage documents that provide direction for end-of-life care and manage other types of Advance Directives.

Description I:

The PHR Account Holder may want to capture and maintain documents that pertain to end-of-life care and to capture and maintain other types of Advance Directives. End-of-life documents include but are not limited to: Advance Directive for Healthcare; Power of Attorney for Healthcare and Physician Order for Life Sustaining Treatment. The system should allow for multiple occurrences of a document and the ability to archive documents. The documents maintained will depend on the jurisdictional law. The documents may or may not reside in the PHR-S. The document may be scanned images, structured documents or simply a notation on the location of the original (hardcopy or original).

Actors:
ehr
Criteria N:
S.3.3.2#01 SHOULD

The system SHOULD provide the ability to capture documents related to end-of-life care and other types of Advance Directives.

Satisfied by:
  1. https://build.fhir.org/ig/HL7/fhir-pacio-adi/
S.3.3.2#02 SHOULD

The system SHOULD provide the ability to render a list of end-of life documents sorted by one or more defined data elements.

S.3.3.2#03 MAY

The system MAY provide the ability to tag a document as Active or Non-Active by category of document.

S.3.3.2#04 SHOULD

The system SHOULD maintain the end-of-life document and/or a note that specifies that document's location.


Source

{
  "resourceType" : "Requirements",
  "id" : "PHRSFMR2-S.3.3.2",
  "meta" : {
    "profile" : [
      "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMFunction"
    ]
  },
  "text" : {
    "status" : "extensions",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Manage documents that provide direction for end-of-life care and manage other types of Advance Directives.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>The PHR Account Holder may want to capture and maintain documents that pertain to end-of-life care and to capture and maintain other types of Advance Directives. End-of-life documents include but are not limited to: Advance Directive for Healthcare; Power of Attorney for Healthcare and Physician Order for Life Sustaining Treatment. The system should allow for multiple occurrences of a document and the ability to archive documents. The documents maintained will depend on the jurisdictional law. The documents may or may not reside in the PHR-S. The document may be scanned images, structured documents or simply a notation on the location of the original (hardcopy or original).</p>\n</div></span>\n \n\n \n <span id=\"actors\"><b>Actors:</b><br/> ehr</span>\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>S.3.3.2#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture documents related to end-of-life care and other types of Advance Directives.</p>\n</div></span>\n \n \n Satisfied by:<ol>\n \n <li><a href=\"https://build.fhir.org/ig/HL7/fhir-pacio-adi/\">https://build.fhir.org/ig/HL7/fhir-pacio-adi/</a></li>\n \n </ol>\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>S.3.3.2#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render a list of end-of life documents sorted by one or more defined data elements.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>S.3.3.2#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to tag a document as Active or Non-Active by category of document.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>S.3.3.2#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD maintain the end-of-life document and/or a note that specifies that document's location.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
  },
  "extension" : [
    {
      "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
      "valueCode" : "ehr"
    }
  ],
  "url" : "http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-S.3.3.2",
  "version" : "2.0.1-ballot",
  "name" : "S_3_3_2_Manage_End_of_Life_Documents_and_Other_Advance_Directives",
  "title" : "S.3.3.2 Manage End-of-Life Documents and Other Advance Directives (Function)",
  "status" : "active",
  "date" : "2025-04-03T15:15:30+00:00",
  "publisher" : "EHR WG",
  "contact" : [
    {
      "telecom" : [
        {
          "system" : "url",
          "value" : "http://www.hl7.org/Special/committees/ehr"
        }
      ]
    }
  ],
  "description" : "Manage documents that provide direction for end-of-life care and manage other types of Advance Directives.",
  "purpose" : "The PHR Account Holder may want to capture and maintain documents that pertain to end-of-life care and to capture and maintain other types of Advance Directives. End-of-life documents include but are not limited to: Advance Directive for Healthcare; Power of Attorney for Healthcare and Physician Order for Life Sustaining Treatment. The system should allow for multiple occurrences of a document and the ability to archive documents. The documents maintained will depend on the jurisdictional law. The documents may or may not reside in the PHR-S. The document may be scanned images, structured documents or simply a notation on the location of the original (hardcopy or original).",
  "statement" : [
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "PHRSFMR2-S.3.3.2-01",
      "label" : "S.3.3.2#01",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : false,
      "requirement" : "The system SHOULD provide the ability to capture documents related to end-of-life care and other types of Advance Directives.",
      "satisfiedBy" : [
        "https://build.fhir.org/ig/HL7/fhir-pacio-adi/"
      ]
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "PHRSFMR2-S.3.3.2-02",
      "label" : "S.3.3.2#02",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : false,
      "requirement" : "The system SHOULD provide the ability to render a list of end-of life documents sorted by one or more defined data elements."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "PHRSFMR2-S.3.3.2-03",
      "label" : "S.3.3.2#03",
      "conformance" : [
        "MAY"
      ],
      "conditionality" : false,
      "requirement" : "The system MAY provide the ability to tag a document as Active or Non-Active by category of document."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "PHRSFMR2-S.3.3.2-04",
      "label" : "S.3.3.2#04",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : false,
      "requirement" : "The system SHOULD maintain the end-of-life document and/or a note that specifies that document's location."
    }
  ]
}

XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.